<html>
<head><meta charset="utf-8"><title>Concerns on nightly in alloc-wg? · t-libs/wg-allocators · Zulip Chat Archive</title></head>
<h2>Stream: <a href="https://rust-lang.github.io/zulip_archive/stream/197181-t-libs/wg-allocators/index.html">t-libs/wg-allocators</a></h2>
<h3>Topic: <a href="https://rust-lang.github.io/zulip_archive/stream/197181-t-libs/wg-allocators/topic/Concerns.20on.20nightly.20in.20alloc-wg.3F.html">Concerns on nightly in alloc-wg?</a></h3>

<hr>

<base href="https://rust-lang.zulipchat.com">

<head><link href="https://rust-lang.github.io/zulip_archive/style.css" rel="stylesheet"></head>

<a name="181322431"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/197181-t-libs/wg-allocators/topic/Concerns%20on%20nightly%20in%20alloc-wg%3F/near/181322431" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Tim Diekmann <a href="https://rust-lang.github.io/zulip_archive/stream/197181-t-libs/wg-allocators/topic/Concerns.20on.20nightly.20in.20alloc-wg.3F.html#181322431">(Nov 21 2019 at 16:38)</a>:</h4>
<p>As the alloc-wg crates grows, I think it makes sense to require a nightly compiler as the feature list grows and many things cannot be used on stable anyway. The biggest downsides so far are <code>dispatch_from_dyn</code>, <code>coerce_unsized</code> and <code>specialization</code> for <code>Vec</code>. Additionally, it will introduce dancing around <code>core::ptr::Unique</code>, as <code>NonNull</code> does not implement <code>Send</code> or <code>Sync</code>. </p>
<p>Are there any concerns not to require the nightly compiler?</p>



<a name="181330685"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/197181-t-libs/wg-allocators/topic/Concerns%20on%20nightly%20in%20alloc-wg%3F/near/181330685" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Gurwinder Singh <a href="https://rust-lang.github.io/zulip_archive/stream/197181-t-libs/wg-allocators/topic/Concerns.20on.20nightly.20in.20alloc-wg.3F.html#181330685">(Nov 21 2019 at 18:07)</a>:</h4>
<p>I agree with using nightly only. The split in code is starting to get bad</p>



<a name="182124501"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/197181-t-libs/wg-allocators/topic/Concerns%20on%20nightly%20in%20alloc-wg%3F/near/182124501" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Simon Sapin <a href="https://rust-lang.github.io/zulip_archive/stream/197181-t-libs/wg-allocators/topic/Concerns.20on.20nightly.20in.20alloc-wg.3F.html#182124501">(Nov 28 2019 at 17:19)</a>:</h4>
<p>Nightly or not, I would recommend against using <code>Unique</code> outside of the standard library, it’s unclear whether it’ll always exist. Explicit impls of <code>Send</code> and <code>Sync</code> on types that contains <code>NonNull</code> should work, would that be satisfactory? Or make your own private newtype of <code>NonNull</code> that implements <code>Send</code> and <code>Sync</code> as needed.</p>



<a name="182130397"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/197181-t-libs/wg-allocators/topic/Concerns%20on%20nightly%20in%20alloc-wg%3F/near/182130397" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Tim Diekmann <a href="https://rust-lang.github.io/zulip_archive/stream/197181-t-libs/wg-allocators/topic/Concerns.20on.20nightly.20in.20alloc-wg.3F.html#182130397">(Nov 28 2019 at 19:05)</a>:</h4>
<p>Good advice, I'll change that.</p>



<hr><p>Last updated: Aug 07 2021 at 22:04 UTC</p>
</html>